Storing Transactional Logs of Fabric Proxy on a Different Disk

Users with the partner or support permission can move Fabric Proxy transactional logs to a different disk. These logs include information about read/write operations to and from the Fabric Proxy.

  1. Enter the sudo rescan-scsi-bus command to detect newly added devices.

  2. Execute one of following commands depending on the number of devices:

    2.1. To add a single device as a transaction log device, enter the command sudo zpool create -o ashift=12 -O atime=off -O canmount=off -O compression=lz4 fablog_pool /dev/sdc -f.

    2.2. To add two devices in the mirror mode as transaction log devices, enter the command sudo zpool create -o ashift=12 -O atime=off -O canmount=off -O compression=lz4 fablog_pool mirror /dev/sdc /dev/sdd -f.

    2.3. To add three devices in the RaidZ mode as transaction log devices, enter the command sudo zpool create -o ashift=12 -O atime=off -O canmount=off -O compression=lz4 fablog_pool raidz /dev/sdc /dev/sdd /dev/sde -f.

  3. The new configurations now get stored in the cache. To load the configurations, export and import zpool using the commands sudo zpool export fablog_pool and sudo zpool import -d /dev/ fablog_pool.

  4. Make a mountpoint and mount it to fablog_pool using the command sudo zfs create -o mountpoint=/opt/commander/fablog fablog_pool/fablog.

  5. Stop the Fabric Proxy service by using the command sudo sv stop zookeeper.

  6. Copy the existing transaction log to a new mountpoint using the command sudo cp -vr /opt/commander/var/zookeeper/log/version-2 /opt/commander/fablog/.

  7. Modify the fabric configuration file to point to the new mountpoint using the command sudo sed -i ‘s/var/zookeeper/log/fablog/’ /opt/commander/installed/zookeeper/conf/zoo.cfg sed -i ‘s/var/zookeeper/log/fablog/’ /ecd tc/service/fabcleanup/run.

  8. Start the Fabric Proxy service using the command sudo sv start zookeeper.

Transactional logs are now stored on a different disk.

Note

  • The Zettabyte File System (ZFS) used in Logpoint Director is a software-defined solution for disk-based redundancy (Mirror, RAIDZ). Logpoint recommends not using hardware-based RAID because it restricts ZFS to only performing self-healing on checksum failures.

  • In RAIDZ mode, the first three disks are used for OS and application installation. Any remaining disks can be used to extend the disk space or as Level 2 Adjustable Replacement Cache (L2ARC) or ZFS Intent Log (ZIL) to enhance ZFS’s read/write performance. Use the ZFS commands to configure any remaining disks.


Helpful?

We are glad this guide helped.


Please don't include any personal information in your comment

Contact Support